Long story short, I'm looking at making poison rules more standardized.
Poisoned: You have disadvantage on attacks and ability checks.
Blighted: You cannot spend hit dice to recover hit points from short or long rests. You cannot make saving throws to remove the poisoned condition.
Standardized Poison Attack
[*] Does X poison damage (save for half)
[*] [Optionally] inflicts poisoned condition on a failed save. You get another saving throw, against the same DC, after a short rest. Failure results in becoming blighted. Once blighted, you need a long rest and a successful saving throw to remove blighted, at the same DC as before.
[*] If you gain the poisoned condition while already under the effects of the same condition, you have disadvantage against your next save to remove the condition at the higher of the two DCs
[*] Additional rider conditions (with their own duration) may happen, depending on the specific poison, but they are automatically removed if the poisoned condition is removed.
5E Poison Standardization Variant
Moderator: Moderators
5E Poison Standardization Variant
Come see Sprockets & Serials
How do you confuse a barbarian?
Put a greatsword a maul and a greataxe in a room and ask them to take their pick
How do you confuse a barbarian?
Put a greatsword a maul and a greataxe in a room and ask them to take their pick
EXPLOSIVE RUNES!
- OgreBattle
- King
- Posts: 6819
- Joined: Sat Sep 03, 2011 9:33 am
So there are no paralyzing, hallucinogenic, type poisons? I pretty much turned poisons into a fortitude save inducing way to inflict various other effects or just damage. I don't think turning it into its own separate status condition is better and would seem more limiting considering the wide range of classic poisonous effects.